Microsoft Sentinel with Firebox Cloud Integration Guide
Microsoft Sentinel is a scalable, cloud-native security information event management (SIEM) and security orchestration, automation, and response (SOAR) solution. Microsoft Sentinel delivers intelligent security analytics and threat intelligence across the enterprise and provides a single solution for alert detection, threat visibility, proactive hunting, and threat response.
This document describes the steps to integrate Microsoft Sentinel with your WatchGuard Firebox Cloud.
Platform and Software
The hardware and software used to complete the steps outlined in this document include:
- Microsoft Sentinel Cloud
- Microsoft Sentinel Agent
- Rsyslog Server
- v8.32.0
- WatchGuard Firebox Cloud
- Fireware v12.8
Test Topology
Before You Begin
Before you begin these procedures, make sure that:
- You have the resource group and workspace configured in Microsoft Sentinel
- You have created a virtual network in the Azure portal
- You have created and configured the rsyslog server
- Your rsyslog server can receive WatchGuard Firebox Cloud logs
- You have a WatchGuard Firebox Cloud deployed on Azure (see Deploy Firebox Cloud on Microsoft Azure)
Set Up Microsoft Sentinel
- Log in to the Azure portal with your Microsoft Azure account credentials.
- Search for and click Microsoft Sentinel.
- Select your workspace.
- Select Configuration > Data connectors.
- Search for and select the WatchGuard Firebox connector.
- Click Open connector page.
- Select the Instructions tab.
- In the Configuration section, expand Install agent on Azure Linux Virtual Machine.
- Click Download & install agent for Azure Linux Virtual machines.
- Select your rsyslog server, and click Connect.
- After a successful connection to your rsyslog server, go back to the WatchGuard Firebox connector page.
- Click Open your workspace agents configuration.
- Select the Syslog tab.
- Click Add facility to add the facilities you need (for example, local0 to local7, kern, and syslog).
- Click Apply.
- Go back to the WatchGuard Firebox connector page, and in the Configuration section, click Follow these steps.
- Copy the values from the WatchGuard syslog Parser page. You need this information in Step 20.
- Close the WatchGuard syslog Parser page, and go back to your Microsoft Sentinel workspace page.
- Select General > Logs.
- Follow the WatchGuard syslog Parser page description, and paste the values from the WatchGuard syslog Parser page into the logs query window.
- Select Save > Save as function.
- In the Function name text box, type WatchGuardFirebox.
- In the Legacy category text box, type WatchGuardFirebox.
- Click Save.
Set Up Firebox Cloud
- Log in to Fireware Web UI (https://<Eth0_public_IP>:8080).
- Select System > Logging.
The Logging page opens. - Select the Syslog Server tab.
- Select the Send log messages to these syslog servers check box.
- Click Add.
The Syslog Server dialogue box opens. - In the IP Address text box, type the IP address of your Microsoft Sentinel Agent.
- In the Port text box, type 514.
- From the Log Format drop-down list, select Syslog.
- Select the syslog facility you need (for example, default settings).
- Click OK.
- Click Save.
You can configure logging in many locations in the Firebox Cloud configuration, such as policies and proxies. Make sure you select Send a log message when you want the Firebox Cloud to generate a log message for an event.
Test the Integration
- After Firebox Cloud begins to send log to Microsoft Sentinel Agent, on the WatchGuard Firebox connector page, select the Next steps tab.
- Select the first query sample. Click Run.
Information about the query appears.
Filter Logs
Information from sources other than the Firebox Cloud can sometimes appear in syslog data. For example, in the query results shown in the Test the Integration section of this document, Ubuntu events are not related to Firebox Cloud. To run a query that returns events from only Firebox Cloud, you can filter the query by host name or computer.
An example query that only includes events from the host name Firebox: